collection

3.1.3.4. Testing results

Most tests passed. We are happy to see our application is compatible with most iCalendar formats generated by other applications.

General issues are:

  • Sequence number:

    • Some CalDAV server/clients assume sequence number starts with 1 instead of 0. We will show a different banner for such case.

    • One client doesn’t have this entry in iCalendar. They said using SEQUENCE is optional for organizer according to RFC 2446.

  • New issues found in our application

    • Dragging event in Month view will cause a wrong Recurrence-ID generated if the series is not in the same time zone as OS’. It doesn’t repro with other views.

Detailed test results:

  • One client doesn’t support modified occurrence and negative exceptions well so far. So most testing is done in single event.

  • Sequence issue mentioned above

  • We have a known issue: EXDATE doesn’t have time zone information

  • Another client said they support WebDAV but we couldn’t connect to it. Most likely they don’t support it fully. They will do more investigation.

    • The exception doesn’t seem to relate to series much except in deletion. Opening or updating such occurrence doesn’t trigger the “for series or for this one” dialog. Important change made to the series(like start/end time or recurring mode) doesn’t overwrite the exceptions. This is a different behavior from other clients.

  • Another client had Sequence inconsistency — single event or recurring series’ sequence starts from 1 and increases for updates. But exception’s in the series starts at 0 and never increases.

  • Recurring All day event from our application is not recognized as “All day” in their application. It is shown as a 0 duration event happening each day. Same event synced to another client is displayed correctly and it doesn’t repro with single all day event in the tested application.

  • One CalDAV server uses RDATE which we do not support. The event can be displayed correctly but the time zone is not recognized.

  • One client had issues with modifying an occurrence in a recurring series that uses a different time zone than calendar time zone. They generate a wrong Recurrence-ID sometimes. They have the same sequence issue noted above.

Overall this is a very interesting and useful InterOP event! Thanks for organizing it!